LogHandler.exe - Background process
Background Job: LogHandler.exe
Introduction
The LogHandler.exe background job is responsible for
truncating the log entries that are made while using e-Synergy. Every action
from every user results in log entries being made in the database. Over time
this can result in a huge database where most of the size is due to log entries
from several years ago. To prevent this Exact has created the LogHandler.exe
background job to reduce the size of the database by deleting old log entries.
More information about setting up this background job can be found in this
document: e-Synergy
and the background applications.
Also the background job updates the overviews of pageviews for documents and applications. This overview can be found in [System >
Reports > Page Views].
Technical Information
The following tables are involved when running LogHandler:
- BacoProcessLog
- BacoAppLogDays
- BacoAppLogHours
- BacoAppLogApps
- BacoAppLog
- BacoErrorLog
- EbcDataLog
- CompanyLogs
- HRErrorLog
- XMLEvents
Every action in e-Synergy results in a log entry made in
the database. LogHandler.exe helps to keep the size of the database down by truncating these log entries based
on settings in e-Synergy. The LogHandler.exe job checks for all log entries the date they were created. If the
entry was created longer then the number of days set in e-Synergy ago, the entry is deleted from the table.
The command line for LogHandler is quite simple. Only the mandatory, standard
parameters are included. The command line will therefore look something like
this:
- C:\Synergy\bin\LogHandler.exe /S:VORS31266-1 /D:DeltaBike
Settings e-Synergy
Based on the settings in e-Synergy via [System > Maintenance > Settings - Database > Log: Truncate] the LogHandler.exe job
truncates the mentioned tables.
These settings determine after how many days log entries are deleted. In the screen you can enter the number of days the entries
should remain in the database.
Troubleshooting
When running the Loghandler.exe - depending on the settings in e-Synergy - records are deleted from the logtables. You expect the database
to decrease in size, but this is not necesseraly the case. SQL is programmed in a way that it reserves free space for new records.
As the size of the tables gets bigger the reserved free space becomes smaller. When the amount of free space is below a certain
percentage SQL takes up more space of the harddrive and the original amount of free space is allocated to the different tables.
When tables are truncated by for example the LogHandler.exe background job SQL doesn't shrink in size to return to the original amount
of free space. Instead it just keeps the extra free space and uses it when the tables get bigger again. Because of this functionality
you might find that the database files aren't smaller after running the LogHandler.exe.
This can be solved by creating a Database Maintenance plan for the database in question. In this Database Maintenance plan you can
make sure SQL removes unused space from the database files when these files grow beyond a certain size. This way you will get harddisk
space back from SQL and you'll see the results of running the LogHandler.
Related Topics
| Main Category: |
Support Product Know How |
Document Type: |
Online help main |
| Category: |
On-line help files |
Security level: |
All - 0 |
| Sub category: |
Details |
Document ID: |
01.694.212 |
| Assortment: |
Exact Synergy
|
Date: |
16-03-2017 |
| Release: |
|
Attachment: |
|
| Disclaimer |